Skip to main navigation Skip to main content Skip to page footer

Participate in a Unit

Units Consist of Unit Members and Unit Supporters

Members and Supporters shape a TYPO3 Unit’s work equally, but accountability sets them apart. Members commit permanently, accept assigned tasks, and vote in the Unit Council. Supporters contribute at their own discretion and need no TYPO3 Association…

How Units Are Organized

Roles, Responsibilities, and Who Decides What

Every TYPO3 Unit has a Coordinator, a Deputy, and a Unit Council, and works within a charter set by the TYPO3 Association Board. Members and Supporters both shape its work, but only Members are accountable for tasks and vote in the Council.

Which Unit Is Right for You?

Find a Unit to Participate In

Feature Unit

The unit drives the functional evolution of the TYPO3 product by researching, identifying, planning, designing, and developing new features and improving existing functionality. It promotes innovation, usability, and a consistent product experience…

Stability & Compliance Unit

The Stability & Compliance Unit is responsible for continuously delivering a stable, secure, accessible and localizable TYPO3 product. It safeguards the quality of every supported TYPO3 version and supports the extension ecosystem in meeting the same…

Ecosystem Unit

The team owns the full lifecycle of the applications and services in the TYPO3 Ecosystem, from infrastructure, development and monitoring through support and the coordinated shutdown of services that are no longer needed. The unit keeps the service…

Knowledge Unit

The unit promotes the adoption, learning, and best-practice use of the TYPO3 product by collecting, documenting, managing, maintaining, and disseminating knowledge about it, its application, APIs, and practical use by editors, developers,…

Content & Communication Unit

The unit promotes the awareness, understanding, and adoption of TYPO3 by creating, writing, proofreading, and publishing content and assets in multiple languages that explains what TYPO3 is, its strengths and differentiators, its place in the market,…

Community Unit

This Unit organizes TYPO3 Association committees representing stakeholder groups or activities outside of product development.

Why TYPO3 Units?

The idea of Units goes back to the TYPO3 CMS Product Strategy. The Governance Working Group turned it into concrete rules, which went through a public community review in August and September 2026. The members of the TYPO3 Association adopted them at the extraordinary General Assembly on 29 October 2026. 

The summary of the public review explains what changed along the way. The rules themselves, each with a detailed FAQ, are in the TYPO3 Policy Directory:

Units do not simply replace the existing teams. The teams built what TYPO3 is today, and the Units keep that work and those people. Existing teams will not be dissolved overnight. Until the end of 2026, there is a transition phase in which their work moves step by step into the new Unit structure. Much of what teams and committees do today will continue as Working Groups within a Unit. What changes is the structure around the work, which spreads the load across more people and makes it easier to join.

The new structure also makes the project quicker to respond. Under the previous team structure, a new team needed months to show it had a right to exist, and budgets were allocated only once a year. Units are organized around broader groups of subject-matter experts. They can act across a whole topic area without waiting for other bodies.